-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: auto-detect Kubernetes schema #962
base: main
Are you sure you want to change the base?
Conversation
automatically detect the Kubernetes schema based on the document's GroupVersionKind (GVK) and retrieve the matching schema from the CRD catalog.
Really nice, even works great with helm-ls (with some small tweaks to helm-ls). I just noticed that it gives an error for normal kubernetes resources, if those are not associated with the correct schema (caused by some config issues).
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please handle the negative test scenarios as well
What does this PR do?
This PR adds an option to automatically detect the Kubernetes schema by parsing the contents of the document. In case a Kubernetes GroupVersionKind (GVK) is detected, the matching schema is retrieved from the CRD catalog.
What issues does this PR fix or reference?
#605
Is it tested? How?
Tests for parsing the Kubernetes Group Version Kind have been added
Please let me know if this can get merged. I think it improves the usability of the langugage server in Kubernetes environments significantly. If there is anything I can change to get this merged, please let me know!